Skip to content

Keep CONFORMANCE.md the requirement table the Part 4 rows are held to - #92

Merged
estebanzimanyi merged 1 commit into
masterfrom
docs/conformance-is-the-requirement-table
Nov 19, 2026
Merged

estebanzimanyi merged 1 commit into
masterfrom
docs/conformance-is-the-requirement-table

Conversation

@estebanzimanyi

Copy link
Copy Markdown
Member

CONFORMANCE.md is the table ats_part4_test.go reads: each requirement of the class cquery, keyed by the draft's number and identifier, with the code that meets it and the test that reads it. What the service declares and answers is stated by the MobilityDB specification doc/specs/mobilityapi-ogc-api.md (MobilityDB/MobilityDB#3836), which carries the aggregations, the lifecycle, the delivery, live ingestion, the streaming engines and the extensions, so the file keeps the table and points to the specification.

The comment on the geometry position stream in routeTable states that no requirement of Part 4 covers it.

The table is the one TestATSPart4RowsAreTheRecordedRequirements reads, row for row.

CONFORMANCE.md keyed each requirement of the class cquery to its code and
test, and also stated the aggregations, the lifecycle, the delivery and the
extensions. What the service answers is stated by the MobilityDB
specification doc/specs/mobilityapi-ogc-api.md, so the file keeps the table
ats_part4_test.go reads and points to the specification for the rest.
@estebanzimanyi
estebanzimanyi merged commit 933880a into master Nov 19, 2026
2 checks passed
@estebanzimanyi
estebanzimanyi deleted the docs/conformance-is-the-requirement-table branch November 19, 2026 14:39
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant